Skip to content

Block Editor: Enqueue script modules via enqueue_block_assets action #10597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
sirreal wants to merge 1 commit into
base: trunk
Choose a base branch
from
Draft

Block Editor: Enqueue script modules via enqueue_block_assets action #10597

sirreal wants to merge 1 commit into from

Conversation

@sirreal
Copy link
Member

@sirreal sirreal commented Dec 4, 2025 •
edited
Loading

Trac ticket: https://core.trac.wordpress.org/ticket/64360

​The enqueue_block_assets action is used to add scripts and styles in the block editor's iframe.

It should be possible to add script modules to the block editor's iframe as well.

See:

_wp_get_iframed_editor_assets and ​its documentation.
The WP_Script_Modules class.
The block editor Iframe component in Gutenberg.
This will likely require a new method or exposing more of the script modules internal data so that a specific WP_Script_Modules instance can be used for the iframed assets. See #60597.

Requires Gutenberg changes to the block editor. See WordPress/gutenberg#73765.

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@sirreal sirreal mentioned this pull request Dec 4, 2025
Draft
@github-actions
Copy link

github-actions bot commented Dec 4, 2025

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@sirreal